home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Celestin Apprentice 4
/
Apprentice-Release4.iso
/
Languages
/
Mops 2.7
/
README.1ST
< prev
Wrap
Text File
|
1995-12-20
|
9KB
|
220 lines
This is Mops 2.7, of December 1996.
This package contains the full Mops system, but not the manual, which
should be available from the same location you got this. It should have
a name something like Mops26m.sea. It's a separate file because of size.
Note that there isn't a manual for 2.7 yet. The current manual is the
2.6 manual. The Release Notes (which you should have here) document
the one major new feature.
You will really need the manual if you're going to do anything with Mops.
This package contains the nucleus as an application, and all the source
code. The nucleus can't be used by itself, but you have to bootstrap
the full system by running the nucleus and using it to compile up everything
else from the source. The reason for this procedure is to reduce the size
of the total package as much as possible - it's big enough already!
The instructions for compiling up the system are give below, and aren't
hard (I hope).
A final reminder: when installing 2.7, if you already have an earlier
Mops version, please remember to remove all copies of the earlier Mops
nucleus. Otherwise, when you double-click on the new Mops.dic, you'll
probably get the wrong nucleus firing up (and you'll crash immediately).
So trash all copies of your older nucleus, or if you're the cautious type,
save a copy on a floppy and eject it.
============================
You should have a folder called "Mops 2.7 system". In this folder there
should be two files and three folders. The two files are this file
(README.1ST) and "Mops 2.7 release notes". The folders are "Mops ƒ",
"Mops Source" and "Quick Edit ƒ".
The "release notes" file is mainly aimed at current Mops users, and
describes the differences in this release, as well as possible future
developments.
"Mops ƒ" contains:
*** The Mops application itself (Mops).
*** The source files which get loaded above the nucleus, but before
HFS file handling is available - Base, Args, Class, Struct, String, Files
and Modules. These must be in the same folder as Mops.
"Mops source" contains all the other Mops source files (of course!!)
The folder "More classes" contains various ex-Neon classes that I
have converted, as well as a number of other classes I have written over
the last few years. Some of these have not been updated to the latest Mops
version, but only minor changes would be needed. There is some code there
which can read and write formatted Microsoft Word documents. I used to need
this capability in my work. By the way, hacking out the MW document format
for versions 1-4 was no joke!! (Yes, the code will read "fast saved"
documents.) But I haven't added Word 5 support, and probably won't ever,
since I've now changed over to Nisus (yes, this is now a Microsoft-free
zone).
"Quick Edit ƒ" contains Doug Hoffman's Quick Edit text editor which
communicates with Mops via Apple events, and related files.
If you don't alter the folder configuration as supplied, things should
work. If you want to put all the Mops stuff into a folder, or change the
folder configuration, you will need to edit the file "Mops.paths" in the
"Mops ƒ" folder - this defines the HFS paths that Mops will use to look for
files.
===============================
Now, here are the instructions for compiling everything, to get you up
and running.
First start up the nucleus application "Mops". You should get a window
appearing on the screen with no menus. The window will be showing a
message telling you that it is only the nucleus, and that you should now
compile the system by typing
load base <ENTER>
and look at the Readme.1st file, or the intro chapter of the manual.
That's exactly what you're doing—so far so good!
So go ahead and type
load base (followed by the <ENTER> key)
This will do the first stage of the compilation. Note that Mops commands
are terminated by <ENTER>, AND THAT <ENTER> IS NOT THE SAME AS <RETURN>!
Many Mac programs treat these two keys as equivalent, but Mops doesn't.
Once you've used Mops for a while you'll come to appreciate the usefulness
of this feature.
.
The compilation will take a couple of minutes. If no errors come up, you'll
get a message saying that interim.dic has been saved, and the ">" prompt
again.
interim.dic is the partial dictionary that has just been compiled. It will
be in the "Mops ƒ" folder.
If something goes wrong in the next stages, you can get back to this point
by double-clicking on interim.dic, without having to go back to the bare
nucleus.
Now, to compile the rest of the dictionary, type
// sys.ld <ENTER>
and everything else should be compiled. It takes about 15 minutes on a
IIsi, so adjust that estimate for whatever Mac you have. In particular,
when you see "Loading ::Mops source:Module source:xcalls" on the screen
it will appear to do nothing for a long while. But don't worry, it
should finish eventually.
The names of the different files will appear on the screen
as they are being compiled. If everything goes OK, at the end of the
compilation you'll get the following message, which should be
self-explanatory:
The Mops system is compiled. Now save the dictionary, by typing e.g.
save Mops.dic
then type bye to quit, and after that you'll be able to fire up the
newly-compiled dictionary.
So do what it says—save the full dictionary by typing
save Mops.dic <ENTER>
In some earlier Mops versions, you could at this point start running the
system. However we now have a new interface, and this needs to be initialized
properly by being started up from the Finder. So quit by typing
bye <ENTER>
Then after that, you can then fire up the "proper" Mops system by
double-clicking on Mops.dic.
Finally, if you use floating point, you can compile it by firing up
Mops.dic and typing
// floating point <ENTER>
and when it's compiled, save with
save MopsFP.dic <ENTER>
After this, you should be able to fire up either the standard or
floating point system by double-clicking on the dictionary image Mops.dic
or MopsFP.dic.
================================
I assemble the nucleus source with Dave McWherter's shareware McAssembly. I
gather it is reasonably compatible with other Mac assemblers. (Unfortunately,
it doesn't work under System 7.) So far nobody else has been brave enough
to actually try reassembling the nucleus, as far as I'm aware. If you find
a bug, it's probably better to simply let me know.
================================
Finally, please note that I am releasing all original Mops material into
the public domain. If you want to use it commercially, that's fine, go
right ahead, but I'd really appreciate it if you could let me know. In
return I could let you know of any late-breaking bugs/fixes which may be
very helpful to you. Also, if you want to include Mops in a CD compilation
of shareware/PD material, that's fine, but it would be good if you could
send me a complimentary copy of your CD.
I'd also like to know about any other Mops development that anyone feels
free to let me know about. Even better, if you develop some whiz-bang new
class or whatever, you could send me a copy and I could make it part of the
standard Mops release. This has already occurred with significant code being
contributed by Doug Hoffman, Greg Haverkamp, Xan Gregg and Jay Farrell. As
a one-man part-time effort, Mops can't hope to compete with the slick commercial
products - but with a bit of cooperation from those using it, Mops could
become a very useful development system, and the price is certainly right.
(So is the performance, I think you'll find.)
Internet and Web info for Mops
------------------------------
If you have internet access, you'll find Mops discussion in the group
comp.lang.forth.mac. Feel free to dive in there. Also note that I
post a FAQ (frequently asked questions) list there every month or so.
See if you can read the latest version of that before emailing me with
a problem, since a lot of questions people ask me are already answered
there. But feel free to email me with compliments at any time!!! :-)
There's a Mops web page at <URL:http://www.netaxs.com/~jayfar/mops.html>.
This has links to the FAQ and the latest Mops version.
For ftp, the latest version should be at:
taygeta.oc.nps.navy.mil, directory pub/Forth/Mops
Finally, if you do have to email me with a problem, remember to tell me
what version you have!
I hope you enjoy Mops.
------------------------------------------------------------------------
Mike Hore mikeh@zeta.org.au _--_|\
/ \
snail-mail: \_.--._x
Michael Hore v
54 Frederick St,
Sydenham NSW 2044,
AUSTRALIA.
------------------------------------------------------------------------